🔗 Linked issue

Resolves #6743

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

First, a root-cause correction for the issue title: no NaN is ever emitted. Committing unparseable text like . or - (Enter/blur) makes reka-ui's NumberField emit undefined — the reporter's isNaN(v) check reads true because isNaN(undefined) is true, and undefined poisons downstream arithmetic into NaN. Reka's applyInputValue conflates two situations that deserve different handling: a cleared input and non-empty unparseable text both nuke the model to undefined (and destroy the previous value).

Two commits, separable:

1. fix(InputNumber): keep previous value when committing unparseable input — what the reporter asked for ("maybe just revert to the previous value instead?"), matching react-spectrum's behavior. All model updates now flow through onUpdate() — previously the auto-forwarded update:modelValue handler bypassed it entirely in non-.optional mode (and double-emitted in .optional mode). When the committed value is undefined but the input still contains text, the update is dropped; since NumberFieldRoot runs controlled, it restores the last formatted value on its own. Verified in the added test: . + Enter on a model of 5 → no emit, input text back to 5.

2. fix(InputNumber): emit null when cleared to match the declared model type — the typing-soundness half reported by @danekslama in the issue comments: the emit type is number | null (undefined only with the .optional modifier), but clearing leaked undefined at runtime regardless. Clearing now emits null, or undefined with .optional (unchanged). This one is mildly behavior-visible for consumers who relied on the untyped undefined — happy to drop this commit if you'd rather keep it wrapper-compatible, the first commit stands alone.

Tests cover all three paths (unparseable revert / clear → null / clear + .optional → undefined); existing suites and snapshots unchanged (110 tests green, vue-tsc clean).

Upstream note: the revert-on-unparseable behavior arguably belongs in reka-ui's applyInputValue eventually, but the wrapper can't wait on that and needs the null convention regardless — no reka-ui issue exists for it yet, I can file one.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.